Using Client Load Balancing

Client load balancing helps distribute new connections in your environment so that no one server is overwhelmed with connection requests. When client load balancing is enabled, the order in which primary and alternate SequeLink servers are tried is random. For example, let us suppose that client load balancing is enabled as shown in Table 5-3:

Figure 5-3. Client Load Balancing Using the JDBC Driver

With load balancing enabled, the connection attempt proceeds from the first alternate SequeLink Server to the second alternate SequeLink Server, then to the primary SequeLink Server.

First, SequeLink Server B is tried (1). Then, SequeLink Server C may be tried (2), followed by a connection attempt to SequeLink Server A (3). In contrast, if client load balancing were not enabled in this scenario, each SequeLink Server would be tried in sequential order, primary server first, then each alternate SequeLink server based on its entry order in the alternate servers list.

For details on configuring client load balancing, refer to the SequeLink Administrator's Guide.